This pull request has merge conflicts. Could you please resolve them @tesol2y090? 🙏

Thanks @tesol2y090!

I think we should first deprecate support for draft-29 before removing it completely, see Step 1 in #3395 (comment).

What is the best way to deprecate support for draft-29, i thought remove the field is ok.

Thanks @tesol2y090!
I think we should first deprecate support for draft-29 before removing it completely, see Step 1 in #3395 (comment).

What is the best way to deprecate support for draft-29, i thought remove the field is ok.

Rust offers the #[deprecated(note = "...")] attribute, which will give the user a warning (used e.g. in #3747).

To deprecate support of draft-29 (which is opt-in anyway), we only need to add this attribute to libp2p_quic::Config::support_draft_29.

Removing draft-29 and all related logic (what this PR is doing) can then be done in a follow-up PR after the next release of libp2p-quic.

Thanks @tesol2y090!
I think we should first deprecate support for draft-29 before removing it completely, see Step 1 in #3395 (comment).

What is the best way to deprecate support for draft-29, i thought remove the field is ok.

Rust offers the #[deprecated(note = "...")] attribute, which will give the user a warning (used e.g. in #3747).

To deprecate support of draft-29 (which is opt-in anyway), we only need to add this attribute to libp2p_quic::Config::support_draft_29.

Removing draft-29 and all related logic (what this PR is doing) can then be done in a follow-up PR after the next release of libp2p-quic.

Thank you @elenaf9 . I just created another #5786 about deprecate support_draft_29